Point to point radio bearers for a broadcasting service

ABSTRACT

A method for establishing a connection between user equipment (UE) and an associated network includes receiving at the UE a notification indicating either a start of a broadcast service or an availability of the broadcast service, such that the notification comprises an identifier which identifies the broadcast service. The method further includes receiving at the UE a setup message which establishes a point-to-point radio bearer between the UE and the network, such that the setup message comprises the identifier which is used to identify that the radio bearer carriers the broadcast service.

CROSS-REFERENCE TO RELATED APPLICATIONS

Pursuant to 35 U.S.C. §119(e), this application claims benefit ofpriority from provisional patent application Ser. No. 60/833,187, filedJul. 24, 2006, the contents of which are hereby incorporated byreference herein in their entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to wireless communicationsystems, and in particular to establishing a connection between userequipment and an associated network.

2. Discussion of the Related Art

A universal mobile telecommunication system (UMTS) is a European-type,third generation IMT-2000 mobile communication system that has evolvedfrom a European standard known as global system for mobilecommunications (GSM). UMTS is intended to provide an improved mobilecommunication service based upon a GSM core network and wideband codedivision multiple access (W-CDMA) wireless connection technology.

In December 1998, a Third Generation Partnership Project (3GPP) wasformed by the ETSI of Europe, the ARIB/TTC of Japan, the T1 of theUnited States, and the TTA of Korea. The 3GPP creates detailedspecifications of UMTS technology. In order to achieve rapid andefficient technical development of the UMTS, five technicalspecification groups (TSG) have been created within the 3GPP forstandardizing the UMTS by considering the independent nature of thenetwork elements and their operations.

Each TSG develops, approves, and manages the standard specificationwithin a related region. Among these groups, the radio access network(RAN) group (TSG-RAN) develops the standards for the functions,requirements, and interface of the UMTS terrestrial radio access network(UTRAN), which is a new radio access network for supporting W-CDMAaccess technology in the UMTS.

FIG. 1 gives an overview of the UMTS network, including the UE, theUTRAN and the core network. The UTRAN is composed of several radionetwork controllers (RNCs) and Node-Bs, which communicate via the Iubinterface.

Each RNC controls several Node-Bs. Each RNC is connected via the Iuinterface to the core network (CN), specifically to the MSC(mobile-services switching center) and the SGSN (serving GPRS supportnode) of the CN. RNCs can be connected to other RNCs via the Iurinterface. The RNC handles the assignment and management of radioresources and operates as an access point with respect to the corenetwork.

The Node-Bs receive information sent by the physical layer of theterminal through an uplink transmission and transmit data to theterminal through a downlink transmission. The Node-Bs operate as accesspoints of the UTRAN for the terminal.

The SGSN is connected via the Gf interface to the EIR (equipmentidentity register), via the GS interface to the MSC, via the GNinterface to the GGSN (gateway GPRS support node) and via the GRinterface to the HSS (home subscriber server). The EIR maintains listsof mobiles that are allowed to be used on the network.

The MSC, which controls the connection for circuit switch (CS) services.The MSC is connected to the MGW (media gateway) via the NB interface, tothe EIR via the F interface, and to the HSS via the D interface. The MGWis connected to the HSS via the C interface and to the PSTN (PublicSwitched Telephone Network). The MGW facilitates adapting the codecsbetween the PSTN and the connected RAN.

The GGSN is connected to the HSS via the GC interface, and to theInternet via the GI interface. The GGSN is responsible for routing,charging, and separation of data flows into different radio accessbearers (RABs). The HSS handles the subscription data of the users.

The UTRAN constructs and maintains a radio access bearer (RAB) forcommunication between the terminal and the core network. The corenetwork requests end-to-end quality of service (QoS) requirements fromthe RAB, and the RAB supports the QoS requirements set by the corenetwork. Accordingly, the UTRAN can satisfy the end-to-end QoSrequirements by constructing and maintaining the RAB.

The services provided to a specific terminal are roughly divided intocircuit switched services and packet switched services. For example, ageneral voice conversation service is a circuit switched service, whilea Web browsing service via an Internet connection is classified as apacket switched service.

For supporting circuit switched services, the RNCs are connected to themobile switching center (MSC) of the core network, and the MSC isconnected to the gateway mobile switching center (GMSC) which managesthe connection with other networks. For supporting packet switchedservices, the RNCs are connected to the serving general packet radioservice (GPRS) support node (SGSN), and the gateway GPRS support node(GGSN) of the core network. The SGSN supports the packet communicationswith the RNCs, and the GGSN manages the connection with other packetswitched networks, such as the Internet.

FIG. 2 illustrates a structure of a radio interface protocol between theterminal and the UTRAN according to the 3GPP radio access networkstandards. As shown in FIG. 2, the radio interface protocol has verticallayers comprising a physical layer, a data link layer, and a networklayer, and has horizontal planes comprising a user plane (U-plane) fortransmitting user data and a control plane (C-plane) for transmittingcontrol information.

The user plane is a region that handles traffic information with theuser, such as voice or Internet protocol (IP) packets. The control planeis a region that handles control information for an interface with anetwork, maintenance and management of a call, and the like.

The protocol layers in FIG. 2 can be divided into a first layer (L1), asecond layer (L2), and a third layer (L3) based on the three lowerlayers of an open system interconnection (OSI) standard model. The firstlayer (L1), or the physical layer, provides an information transferservice to an upper layer by using various radio transmissiontechniques. The physical layer is connected to an upper layer, called amedium access control (MAC) layer, via a transport channel.

The MAC layer and the physical layer exchange data via the transportchannel. The second layer (L2) includes a MAC layer, a radio linkcontrol (RLC) layer, a broadcast/multicast control (BMC) layer, and apacket data convergence protocol (PDCP) layer.

The MAC layer handles mapping between logical channels and transportchannels, and provides allocation of the MAC parameters for allocationand re-allocation of radio resources. The MAC layer is connected to anupper layer, called the radio link control (RLC) layer, via a logicalchannel.

Various logical channels are provided according to the type ofinformation transmitted. In general, a control channel is used totransmit information of the control plane, and a traffic channel is usedto transmit information of the user plane.

A logical channel may be a common channel or a dedicated channeldepending on whether the logical channel is shared. Logical channelsinclude a dedicated traffic channel (DTCH), a dedicated control channel(DCCH), a common traffic channel (CTCH), a common control channel(CCCH), a broadcast control channel (BCCH), and a paging control channel(PCCH) or a shared channel control channel.

The BCCH provides information including information utilized by aterminal to access a system. The PCCH is used by the UTRAN to access aterminal.

For the purposes of a multimedia broadcast/multicast service (MBMS)additional traffic and control channels are introduced in the MBMSstandard. The MCCH (MBMS point-to-multipoint control channel) is usedfor transmission of MBMS control information. The MTCH (MBMSpoint-to-multipoint traffic channel) is used for transmitting MBMSservice data. The MSCH (MBMS Scheduling Channel) is used to transmitscheduling information. The different logical channels that exist arelisted in FIG. 3.

The MAC layer is connected to the physical layer by transport channelsand can be divided into a MAC-b sub-layer, a MAC-d sub-layer, a MAC-c/shsub-layer, a MAC-hs sub-layer and a MAC-m sublayer according to the typeof transport channel being managed. The MAC-b sub-layer manages a BCH(broadcast channel), which is a transport channel handling thebroadcasting of system information. The MAC-c/sh sub-layer manages acommon transport channel, such as a forward access channel (FACH) or adownlink shared channel (DSCH), which is shared by a plurality ofterminals, or in the uplink the radio access channel (RACH). The MAC-msublayer may handle the MBMS data.

The possible mapping between the logical channels and the transportchannels from a UE perspective is given in FIG. 4. The possible mappingbetween the logical channels and the transport channels from a UTRANperspective is given in FIG. 5.

The MAC-d sub-layer manages a dedicated channel (DCH), which is adedicated transport channel for a specific terminal. The MAC-d sublayeris located in a serving RNC (SRNC) that manages a correspondingterminal. One MAC-d sublayer also exists in each terminal.

The RLC layer, depending of the RLC mode of operation, supports reliabledata transmissions and performs segmentation and concatenation on aplurality of RLC service data units (SDUs) delivered from an upperlayer. When the RLC layer receives the RLC SDUs from the upper layer,the RLC layer adjusts the size of each RLC SDU in an appropriate mannerbased upon processing capacity and then creates data units by addingheader information thereto. The data units, called protocol data units(PDUs), are transferred to the MAC layer via a logical channel. The RLClayer includes a RLC buffer for storing the RLC SDUs and/or the RLCPDUs.

The BMC layer schedules a cell broadcast (CB) message transferred fromthe core network and broadcasts the CB message to terminals positionedin a specific cell or cells.

The PDCP layer is located above the RLC layer. The PDCP layer is used totransmit network protocol data, such as the IPv4 or IPv6, effectively ona radio interface with a relatively small bandwidth. For this purpose,the PDCP layer reduces unnecessary control information used in a wirednetwork, a function called header compression.

The radio resource control (RRC) layer located at the lowest portion ofthe third layer (L3) is only defined in the control plane. The RRC layercontrols the transport channels and the physical channels in relation tosetup, reconfiguration, and the release or cancellation of the radiobearers (RBs). Additionally the RRC handles user mobility within the RANand additional services, such as location services.

The RB signifies a service provided by the second layer (L2) for datatransmission between the terminal and the UTRAN. In general, the set upof the RB refers to the process of stipulating the characteristics of aprotocol layer and a channel required for providing a specific dataservice, and setting the respective detailed parameters and operationmethods.

The different possibilities that exist for the mapping between the radiobearers and the transport channels for a given UE are not all possibleall the time. The UE and UTRAN deduce the possible mapping depending onthe UE state and the procedure that the UE and UTRAN are executing. Thedifferent states and modes are explained in more detail below, as far asthey concern the present invention.

The different transport channels are mapped onto different physicalchannels. For example, the RACH transport channel is mapped on a givenPRACH, the DCH can be mapped on the DPCH, the FACH and the PCH can bemapped on the S-CCPCH, and the DSCH is mapped on the PDSCH. Theconfiguration of the physical channels is given by RRC signalingexchange between the RNC and the UE.

The RRC mode refers to whether there exists a logical connection betweenthe RRC of the terminal and the RRC of the UTRAN. If there is aconnection, the terminal is said to be in RRC connected mode. If thereis no connection, the terminal is said to be in idle mode.

Because an RRC connection exists for terminals in RRC connected mode,the UTRAN can determine the existence of a particular terminal withinthe unit of cells. For example, the UTRAN can determine in which cell orset of cells an RRC connected mode terminal is located and to whichphysical channel the UE is listening. Thus, the terminal can beeffectively controlled.

In contrast, the UTRAN cannot determine the existence of a terminal inidle mode. The existence of idle mode terminals can only be determinedby the core network to be within a region that is larger than a cell,for example, a location or a routing area. Therefore, the existence ofidle mode terminals is determined within large regions, and in order toreceive mobile communication services such as voice or data, the idlemode terminal must move or change into the RRC connected mode. Thepossible transitions between modes and states are shown in FIG. 6.

A UE in RRC connected mode can be in different states, such as CELL_FACHstate, CELL_PCH state, CELL_DCH state, or URA_PCH state. Depending onthe state, the UE carries out different actions and listens to differentchannels.

For example, a UE in CELL_DCH state will try to listen to DCH type oftransport channels, among others. DCH types of transport channelsinclude DTCH and DCCH transport channels, which can be mapped to acertain DPCH, DPDSCH or other physical channels.

The UE in CELL_FACH state will listen to several FACH transportchannels, which are mapped to a certain S-CCPCH. A UE in PCH state willlisten to the PICH channel and the PCH channel, which are mapped to acertain S-CCPCH physical channel.

The main system information is sent on the BCCH logical channel which ismapped on the P-CCPCH (primary common control physical channel).Specific system information blocks can be sent on the FACH channel. Whenthe system information is sent on FACH, the UE receives theconfiguration of the FACH either on the BCCH that is received on P-CCPCHor on a dedicated channel. When system information is sent on the BCCH(i.e,. via the P-CCPCH), then in each frame or set of two frames the SFN(system frame number) is sent which is used in order to share the sametiming reference between the UE and the Node-B. The P-CCPCH is sentusing the same scrambling code as the P-CPICH (primary common pilotchannel), which is the primary scrambling code of the cell. Thespreading code that is used by the P-CCPCH is of a fixed SF (spreadingfactor) 256, and the number is one. The UE knows about the primaryscrambling code either by information sent from the network on systeminformation of neighboring cells that the UE has read, by messages thatthe UE has received on the DCCH channel, or by searching for theP-CPICH, which is sent using the fixed SF 256, the spreading code number0 and which transmits a fixed pattern.

The system information comprises information on neighboring cells,configuration of the RACH and FACH transport channels, and theconfiguration of MICH and MCCH which are channels that are dedicatedchannels for the MBMS service.

Each time the UE changes the cell it is camping (in idle mode) or whenthe UE has selected the cell (in CELL_FACH, CELL_PCH or URA_PCH) state,the UE verifies that it has valid system information. The systeminformation is organized in SIBs (system information blocks), a MIB(master information block) and scheduling blocks. The MIB is sent veryfrequently and gives timing information of the scheduling blocks and thedifferent SIBs. For SIBs that are linked to a value tag, the MIB alsocontains information on the last version of a part of the SIBs. SIBsthat are not linked to a value tag are linked to an expiration timer.SIBs linked to an expiration timer become invalid and need to be rereadif the time of the last reading of the SIB is larger than this timervalue. SIBs linked to a value tag are only valid if they have the samevalue tag as the one broadcast in the MIB. Each block has an area scopeof validity (cell, PLMN, equivalent PLMN) which signifies on which cellsthe SIB is valid. A SIB with area scope “cell” is valid only for thecell in which it has been read. A SIB with area scope “PLMN” is valid inthe whole PLMN, a SIB with the area scope “equivalent PLMN” is valid inthe whole PLMN and equivalent PLMN.

In general UEs read the system information when they are in idle mode,CELL_FACH state, CELL_PCH state or in URA_PCH state of the cells thatthey have selected or the cell that they are camping on. In the systeminformation, they receive information on neighboring cells on the samefrequency, different frequencies and different RAT (radio accesstechnologies). This allows the UE to know which cells are candidates forcell reselection.

MBMS is introduced in the UMTS standard in the Release 6 of thespecification (Rel-6). It describes techniques for optimizedtransmission of MBMS bearer service including point-to-multipointtransmission, selective combining and transmission mode selectionbetween point-to-multipoint and point-to-point bearers. This is used inorder to save radio resources when the same content is sent to multipleusers, and enables TV-like services. MBMS data can be split into twocategories, control plane information and user plane information. Thecontrol plane information contains information on the physical layerconfiguration, transport channel configuration, radio bearerconfiguration, ongoing services, counting information, schedulinginformation, and the like. In order to allow UEs to receive thisinformation, MBMS bearer specific control information for the MBMS issent to the UEs.

The user plane data of MBMS bearers can be mapped onto dedicatedtransport channels for a point-to-point service which is sent only toone UE, or on a shared transport channel for point to multipoint servicewhich is transmitted to (and received by) several users at the sametime.

Point-to-point transmission is used to transfer MBMS specificcontrol/user plane information, as well as dedicated control/user planeinformation between the network and a UE in RRC connected mode. It isused for the multicast or the broadcast mode of MBMS. DTCH is used for aUE in CELL_FACH and Cell_DCH. This allows existing mappings to transportchannels.

To allow cell resources to be used in an optimized manner, a functioncalled counting has been introduced in MBMS applications. The countingprocedure is used to determine how many UEs are interested in thereception of a given service. This is done by using the countingprocedure shown in FIG. 7.

For example, a UE that is interested in a certain service receivesinformation of the availability of a MBMS service. The network caninform the UE that it should indicate to the network its interest in theservice in the same way such as by transmitting the “access information”on the MCCH channel. A probability factor included in the accessinformation message determines that an interested UE will only respondwith a given probability. In order to inform the network that the UE isinterested in a given service, the UE will send to the network the RRCconnection setup message or the cell update message in the cell that theUE has received the counting information. This message may potentiallyinclude an identifier indicating the service that the UE is interestedin.

Point-to-multipoint transmission is used to transfer MBMS specificcontrol/user plane information between the network and several UEs inRRC connected or idle mode. It is used for broadcast or multicast modeof MBMS.

In the case that the network operates on several frequencies, when a UEis camping on one frequency, and a MBMS service is transmitted on adifferent frequency, a UE may not be aware of the fact that a MBMSservice is transmitted in the different frequency. Therefore thefrequency convergence procedure allows the UE to receive information infrequency A that indicates in a frequency B that a given service isavailable.

SUMMARY OF THE INVENTION

Features and advantages of the invention will be set forth in thedescription which follows, and in part will be apparent from thedescription, or may be learned by practice of the invention. Theobjectives and other advantages of the invention will be realized andattained by the structure particularly pointed out in the writtendescription and claims hereof as well as the appended drawings.

In accordance with an embodiment, a method for establishing a connectionbetween user equipment (UE) and an associated network includes receivingat the UE a notification indicating either a start of a broadcastservice or an availability of the broadcast service, such that thenotification comprises an identifier which identifies the broadcastservice. The method further includes receiving at the UE a setup messagewhich establishes a point-to-point radio bearer between the UE and thenetwork, such that the setup message includes the identifier which isused to identify that the radio bearer carriers the broadcast service.

One feature includes sending a request message to the networkidentifying the broadcast service for the UE.

Another feature includes establishing or maintaining a signalingconnection between the UE and the network.

Yet another feature includes sending a setup confirmation message to thenetwork to confirm establishment of the broadcast service.

Still yet another feature includes the notification includes at leastone of a MODIFIED SERVICES INFORMATION message and an UNMODIFIEDSERVICES INFORMATION message.

According to one aspect, the broadcast service is a multimediabroadcast/multicast service (MBMS).

According to another aspect the user equipment (UE) and the network areconfigured to operate within a universal mobile telecommunicationssystem (UMTS).

According to yet another aspect, the request message includes a messageselected from the group consisting of a cell update message, a RRCconnection request message, and a multimedia broadcast/multicast service(MBMS) modified service request message.

According to still yet another aspect, the notification includes aversion of service information having the identifier, and the methodfurther includes creating at least one short transmission data, suchthat the at least one short transmission data references the identifier,and transmitting a request message to the network, such that the requestmessage comprises the at least one short transmission data along withversion information associated with the version of the serviceinformation, such that the short transmission data identifies thebroadcast service.

One feature includes determining the version of the service informationusing a timing reference associated with the service information.

According to one aspect the timing reference is determined based upon asystem frame number associated with the service information.

According to another aspect the service information includes a list ofservice identifiers arranged by appending service identifiers receivedin unmodified services information to service identifiers received inmodified services information.

According to yet another aspect the at least one short transmissionidentifier corresponds to a location of the at least one serviceidentifier within the list of service identifiers.

According to still yet another aspect the identifier includes atemporary mobile group identifier (TMGI).

In accordance with an alternative embodiment, a method for establishinga connection between user equipment (UE) and an associated networkincludes transmitting to the UE a notification indicating either a startof a broadcast service or an availability of the broadcast service, suchthat the notification includes an identifier which identifies thebroadcast service, and transmitting to the UE a setup message whichestablishes a point-to-point radio bearer between the UE and thenetwork, such that the setup message comprises the identifier which isused to identify that the radio bearer carriers the broadcast service.

In accordance with another alternative embodiment, a method forestablishing a connection between user equipment (UE) and an associatednetwork includes receiving at the UE a service announcement providing adescription of an available broadcast service and at least oneidentifier which identifies the broadcast service, and receiving at theUE a setup message which establishes a point-to-point radio bearerbetween the UE and the network, such that the setup message comprisesthe identifier which is used to identify that the radio bearer carriersthe broadcast service.

In accordance with still yet another embodiment, a method fortransmitting a service identifier from user equipment (UE) to anassociated network includes receiving at the UE a version of serviceinformation, the service information includes at least one serviceidentifier, creating at least one short transmission identifier, suchthat the at least one short transmission identifier references at leastone service identifier of the service information, and transmitting theat least one short transmission identifier to the network along withversion information associated with the version of the serviceinformation.

In accordance with one embodiment, a method for decoding a shorttransmission identifier in a network includes transmitting to the UE aversion of service information, the service information includes atleast one service identifier, receiving at least one short transmissionidentifier and version information at the network, such that the atleast one short transmission identifier references at least one serviceidentifier of the service information, and such that the versioninformation is associated with the version of the service information,decoding the least one short transmission identifier based upon and theversion information to identify the at least one service identifier.

These and other embodiments will also become readily apparent to thoseskilled in the art from the following detailed description of theembodiments having reference to the attached figures, the invention notbeing limited to any particular embodiment disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this specification, illustrate embodiments of the invention andtogether with the description serve to explain the principles of theinvention. Features, elements, and aspects of the invention that arereferenced by the same numerals in different figures represent the same,equivalent, or similar features, elements, or aspects in accordance withone or more embodiments. In the drawings:

FIG. 1 illustrates a conventional UMTS network;

FIG. 2 illustrates a conventional radio interface protocol between a UEand UTRAN;

FIG. 3 illustrates a logical channel structure;

FIG. 4 illustrates possible mappings between logical channels andtransport channels from the UE perspective;

FIG. 5 illustrates possible mappings between logical channels andtransport channels from the UTRAN perspective;

FIG. 6 illustrates possible UE state transitions;

FIG. 7 illustrates a typical counting procedure;

FIG. 8 is a block diagram of a process for providing a particular MBMSservice using multicast mode;

FIG. 9 is a block diagram of a process for providing broadcast services;

FIG. 10 provides an example of joining and MBMS context activation for amulticast service;

FIG. 11 provides an example of a PtP radio bearer setup for multicastservices;

FIG. 12 depicts an example of a typical network service access pointidentifier (NSAPI);

FIG. 13 depicts an example of a typical enhanced NSAPI, which iscommonly used in MBMS;

FIG. 14 depicts an example of a typical temporary mobile group identity(TMGI);

FIG. 15 depicts an example of a PtP radio bearer setup for broadcastservices utilizing TMGI in a radio bearer setup message, in accordancewith an embodiment of the present invention;

FIG. 16 depicts an example of a PtP radio bearer setup for broadcastservices utilizing TMGI in the announcement, in accordance with anembodiment of the present invention;

FIG. 17 depicts an example of a PtP radio bearer setup for broadcastservices utilizing an MBMS short identifier for the indication of aservice, in accordance with an embodiment of the present invention; and

FIG. 18 is a block diagram of mobile communication device 300, which maybe configured as a UE in accordance with embodiments of the presentinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or similar parts.

Embodiments of the present invention include various techniques forlinking a MBMS bearer service to a PtP radio bearer. This allows, amongother things, the UE to receive a dedicated bearer carrying a MBMSservice without the need to join the service beforehand. A networkoperating in accordance with the 3GPP standards, for example, providesmultimedia broadcast multicast service (MBMS). This service has beenimplemented relatively recently, an example of which is described inRelease 6 of the 3GPP standards. The 3GPP TSG SA (Service and SystemAspect) describes various network components and associated functionsfor supporting MBMS services. A typical Release 99 cell broadcastservice is limited to broadcasts relating to text-based messaging. TheMBMS service of Release 6 is more advanced in that the networkmulticasts multimedia data to terminals (e.g., UEs) that have subscribedto the corresponding service. Broadcasting of multimedia data is alsopossible.

In general, the MBMS service is a downward-dedicated service thatprovides a streaming or background service to a plurality of terminalsusing a common or dedicated downward channel. The MBMS service may begenerally divided into a broadcast mode and a multicast mode.

MBMS broadcast mode may be used to transmit multimedia data to userslocated within the broadcast area, while MBMS multicast mode transmitsmultimedia data to a specific user group located within the multicastarea. The broadcast area relates to an area in which the broadcastservice is available, and the multicast area relates to an area in whichthe multicast service is available.

FIG. 8 is a block diagram of a process for providing a particular MBMSservice using multicast mode. This process has two general types ofactions; transparent and nontransparent.

One transparent action relates to a situation in which a user desiringto receive a MBMS service will need to first subscribe to the desiredMBMS service or services. A service announcement may provide theterminal with a list of possible MBMS services and related information.The user can then join these services, resulting in the user becoming amember of a multicast service group. If a user is not interested in agiven MBMS service, the user can then leave the service such that theuser is no longer a member of the multicast service group. Thesetransparent actions can be achieved using any of a variety of differentcommunication types (e.g., short message service (SMS), Internetcommunications, and the like), and do not necessarily require use of theUMTS system, for example.

Actions which are nontransparent to the UTRAN (i.e., actions which areknown to the UTRAN) include session start, MBMS notification, datatransfer, and session termination. For instance, the SGSN may inform theRNC about the start of a session. The RNC may then notify the variousUEs of the multicast group that a given service has started so that suchUEs may initiate the reception of the service. Once a UE has initiatedreception of the multicast service, data transmission commences. Atsession termination, the SGSN indicates this action to the RNC, which inturn initiates session termination. Transmission of the service from theSGSN relates to the RNC providing a radio bearer service to convey theMBMS service data.

After the notification procedure, a number of procedures may beinitiated between the UE, the RNC, and the SGSN in order to enable datatransmission. Examples of such procedures include RRC connectionestablishment, connection establishment toward the packet switcheddomain, frequency layer convergence, counting, and the like.

It should be noted that reception of a MBMS service may be performed inparallel to the reception of other services (e.g., voice or videotransmission on the circuit switched domain, SMS transfer on the circuitswitched or packet switched domain, data transfer on the packet switcheddomain, or any signaling related to the UTRAN, packet switch domain, orcircuit switch domain).

FIG. 9 is a block diagram of a process for providing broadcast services.In contrast to the multicast process of FIG. 8, the broadcast service ofFIG. 9 depicts providing service announcement in a transparent manner.No subscription or joining is required for the broadcast service.Actions which are nontransparent for the broadcast services are similarto those in the multicast process of FIG. 8.

Another difference is that for multicast services, the UE may previouslysubscribe to the service such that the network is aware of UEs which areinterested in a given service before the service actually starts.Conversely, in broadcast services, the network is not made aware of UEswhich are interested in a service until the service starts.

If the network has determined that a service should be sent on a PtPbearer, and the service starts, the network will typically inform the UEthat it should request the establishment of the PtP service. This istypically accomplished by sending a notification message to the UE, suchas a MODIFIED SERVICES INFORMATION or MBMS UNMODIFIED SERVICESINFORMATION message, for example.

FIG. 10 provides an example of joining and MBMS context activation for amulticast service. Operation 105 includes the UE joining the multicastservice, and in particular, the UE indicates to the GGSN that it wantsto receive the multicast service. The GGSN checks the authorization withthe BM-SC, and informs the SGSN on the joining procedure. Operation 110relates to the SGSN sending the request MBMS context activation messageto the UE. This message requests that the UE activate the service in theSGSN. Operation 115 shows the UE acknowledging the request MBMS contextactivation message and sending a MBMS context activation requestmessage. This message typically includes, for example, a temporarymobile group identifier (TMGI), and an enhanced network service accesspoint identifier (ENSAPI). The network confirms the MBMS contextactivation request message by sending an activate MBMS context acceptmessage to the UE (operation 120).

At this point, the ENSAPI is effectively linked to a TMGI, and thus,there is no need to transmit the TMGI to the UE at the establishment ofa PtP bearer. That is, the transmission of the ENSAPI at the PtP bearerestablishment from the RNC to the UE is sufficient to identify the TMGIthat has been linked to the ENSAPI in the earlier context establishment.

FIG. 11 provides an example of PtP radio bearer setup for multicastservices. The serving RNC is shown informing the UE that a new orexisting service is present. Typically, the TMGI or some representationof the TMGI is transmitted to the UE (operation 150). Because the TMGIincludes the PLMN identification, the PLMN identification portion of theTMGI may be omitted if this identification is the same as that of one ofthe PLMN IDs of the network.

Operation 155 depicts the UE requesting a radio bearer setup. If the UEhas not already established a connection to the Iu interface, the UEinitiates this establishment in operation 160.

Operation 165 relates to the RNC exchanging linking information with theSGSN, such that for each service identified by the TMGI that the UE hassubscribed, the RNC has an (E)NSAPI value available. This is desirablebecause the size of the TMGI value is typically much larger than thesize of the (E)NSAPI. Operation 170 provides a radio bearer setupmessage which includes the (E)NSAPI and TMGI. Operation 175 includesmapping of the established radio bearer to the TMGI based upon the(E)NSAPI. In operation 180, the UE confirms the establishment with aradio bearer setup complete message transmitted to the SRNC.

FIG. 12 depicts an example of a typical network service access pointidentifier (NSAPI). As this figure illustrates, the NSAPI includescertain unused portions. In particular, only locations 5-15, of the 0-15possible locations, are used. FIG. 13 depicts an example of a typicalenhanced NSAPI, which is commonly used in the MBMS. The enhanced NSAPIshown in this figure is coded on 8 octets. From the available values0-255, only values 128-255 are used for MBMS. Accordingly, the NSAPI andenhanced NSAPI may be similarly utilized and will be referred to hereinas (E)NSAPI.

FIG. 14 depicts an example of a typical temporary mobile group identity(TMGI). A mobile counter code (MCC) and a mobile network code (MNC)collectively define a PLMN code. The PLMN code in a TMGI in many caseswill be the same as the PLMN code of the network with which the UE hasregistered. Thus it is possible to omit the MCC and MNC (i.e., the PLMNin the case that it is the same as the PLMN of the network, or a PLMNthat is listed in the network such as the case in shared networks).

In general, UE linking in a broadcast service (e.g., such as that whichis illustrated in FIG. 11), is not utilized. Accordingly, if the networkis to carry a MBMS broadcast service on a PtP bearer, the (E)NSAPI thatis used in the radio bearer setup will not have been defined beforehand.A potential issue is that different UEs might be interested in differentservices, and thus, a fixed mapping from the (E)NSAPI to the TMGI istypically not used.

In accordance with various embodiments of the present invention, severalgeneral techniques for resolving the noted issue, among other issues,will now be described. A first technique includes adding the TMGI, or arepresentation of the TMGI, to a radio bearer setup message. This may beused to identify, for each radio bearer, whether the (E)NSAPI is used.This in turn permits the identification of the MBMS or other servicethat the radio bearer carries. This further permits the UE to identifythe MBMS service transported in the radio bearer. However, thisarrangement typically requires a significant increase of the messagesize because of the size of the TMGI.

A second technique includes the network indicating an (E)NSAPI alongwith each TMGI, or representation of the TMGI. This indication istypically sent to the UE in a notification message of a broadcastservice. Some of the (E)NSAPI values are typically reserved for use asactive broadcast services such that they are not used during the linkingphase.

A third technique has the UE indicating a linking between the (E)NSAPIand the TMGI directly toward the RNC.

FIG. 15 depicts an example of a PtP radio bearer setup for broadcastservices utilizing TMGI in a radio bearer setup message, in accordancewith an embodiment of the present invention. Operation 200 includesinforming the UE of the start of session of a MBMS service. Thisoperation may further indicate that the service is to be sent on a PtPradio bearer. This may be accomplished using by the network transmittinga message such as, for example, a MODIFIED SERVICES INFORMATION or MBMSUNMODIFIED SERVICES INFORMATION message.

At operation 205 the UE requests a PtP bearer using a suitable message(e.g., cell update, RRC connection request message, MBMS modifiedservice request, and the like) which includes the TMGI (or otheridentifier). Such a message is typically utilized to indicate to theserving RNC which service the UE would like to receive. If desired, theUE may initiate the establishment of an RRC and Iu connection if suchprocesses have not previously been done (operation 210).

According to operation 215, the RNC initiates a radio bearer setup usinga radio bearer setup message. According to one aspect of the presentinvention, this message may include the TMGI (or an identifier derivedfrom the TMGI) which identifies the service which is to be carried bythe radio beater. The radio bearer setup is now complete (operation220). Interestingly, the UE can thus identify the service without usingthe (E)NSAPI. Note that (E)NSAPI is commonly included in the radiobearer setup message, even if such parameters are not used. It maytherefore be useful to reuse the (E)NSAPI value.

FIG. 16 depicts an example of a PtP radio bearer setup for broadcastservices utilizing TMGI in the announcement, in accordance with anembodiment of the present invention. Operation 250 includes informingthe UE of the start of a session of a MBMS service. This operation mayfurther include an indication that the service will be sent on a PtPbearer. If desired, the network allocates an (E)NSAPI value of areserved set of values, or a value that is not yet used by the UE, forthe MBMS broadcast service. The mapping between the (E)NSAPI value andthe TMGI is typically valid as long as the broadcast service is active.

According to operation 255, the UE requests a PtP bearer using asuitable message or request which indicates that the UE is interested inreceiving MBMS broadcast service on a PtP radio bearer. Such a requestmay be implemented using cell update, RRC connection request, MBMSmodified service request message, and the like.

To indicate the service that the UE is interested in, a TMGI or aderived value may also be included in the request. Alternatively, if the(E)NSAPI has already been allocated, the (E)NSAPI may be used toidentify the service requested by the UE. Yet another alternativerelates to the scenario in which the UE has not yet received the(E)NSAPI. In such a scenario, the UE could indicate the TMGI and(E)NSAPI that would be allocated for that MBMS service.

Operation 260 relates to the UE initiating the establishment of an RRCand Iu connection, if such actions have not already been performed.Operation 265 specifies the RNC initiating the radio bearer setup using,for example, the radio bearer setup message. If desired, this messagemay include the (E)NSAPI that the network had previously sent to the UEor that the UE has indicated to the network in combination with the(E)TMGI. Operation 270 includes mapping of the established radio bearerto the TMGI based upon the (E)NSAPI. The UE can thus identify theservice using the (E)NSAPI. If desired the UE may indicate thesuccessful establishment of the radio bearer by sending a radio bearersetup complete message to the network (operation 275).

In accordance with further embodiments of the present invention, insteadof including the TMGI value in a cell update message or RRC connectionsetup message, a MBMS short transmission identification may becalculated. Such calculations may be based on, for example, the order ofthe entries in the MBMS MODIFIED SERVICES INFORMATION and MBMSUNMODIFIED SERVICES INFORMATION messages.

The MBMS short transmission identification is typically used in thedownlink. This is usually implemented to avoid repeating the completeTMGI listed in the MBMS MODIFIED SERVICES INFORMATION or MBMS UNMODIFIEDSERVICES INFORMATION message sent on the MCCH channel when it needs tobe listed in the MBMS ACCESS INFORMATION message (which is also sent onthe MCCH channel). In that case, the UE may calculate the meaning of theMBMS short transmission identification sent in the MBMS ACCESSINFORMATION message by concatenating the TMGIs listed in the MBMSMODIFIED SERVICES INFORMATION and MBMS UNMODIFIED SERVICES INFORMATION.The value of the MBMS short transmission identification provides theentry of the TMGI in that list.

Thus, instead of including the TMGI listed in the uplink (e.g., via thecell update, RRC connection request, MBMS modified service request orany other message), the UE may include the entry of the TMGI in the listof the MBMS MODIFIED SERVICES INFORMATION message, or an entry of thelist of TMGIs in the MBMS UNMODIFIED SERVICES INFORMATION message, inaddition to the total number of TMGIs listed in the MBMS MODIFIEDSERVICES INFORMATION message. Because the content of the MBMS MODIFIEDSERVICES INFORMATION and MBMS UNMODIFIED SERVICES INFORMATION messagesmay change over time, it may be useful to additionally include a timingreference so that the network has knowledge of which version of theMODIFIED SERVICES INFORMATION and MBMS UNMODIFIED SERVICES INFORMATIONthe MBMS short transmission identification refers. These and otheraspects will now be described with regard to FIG. 17.

FIG. 17 depicts an example of a PtP radio bearer setup for broadcastservices utilizing a MBMS short identifier for the indication of aservice, in accordance with an embodiment of the present invention.Operation 280 includes the UE receiving MBMS modified and unmodifiedservice information messages during a modification period (i.e., duringa period in which the UE knows that the contents will not change).According to operation 285, the UE can then calculate the MBMS shorttransmission identification. In operation 290, the UE transmits an RRCconnection request message or cell update message to the network. Thismessage may include the MBMS short transmission identification. It ispossible for a delay to be present in the transmission of this message,and thus, the MBMS modified and unmodified service information messagestransmitted at the time where the RNC receives the message might bedifferent compared to the MBMS modified and unmodified serviceinformation messages transmitted at the time where the UE has calculatedthe MBMS short transmission ID.

Operation 295 allows the RNC to decode the message based on the correctmodification period. One technique for accomplishing this is to includea timing reference in the message. This timing reference indicates onwhich the MBMS modified and unmodified service information messages theMBMS short transmission ID has been created. Such a timing reference mayinclude, for example, a system frame number (SFN), or portions of a SFNwhich are broadcast on BCH channels in the UMTS.

FIG. 18 is a block diagram of mobile communication device 300, which maybe configured as a UE in accordance with embodiments of the presentinvention. Device 300 is illustrated, for example, as a mobile phone andmay be configured to perform various methods described herein. Themobile communication device 300 includes a processing unit 310 such as amicroprocessor or digital signal processor, RF module 335, powermanagement module 305, antenna 340, battery 355, display 315, keypad320, optional subscriber identify module (SIM) card 325, memory unit 330such as flash memory, ROM or SRAM, speaker 345 and microphone 350.

A user enters instructional information, such as a telephone number, forexample, by pushing the buttons of keypad 320 or by voice activationusing microphone 350. Processing unit 310 receives and processes theinstructional information to perform the appropriate function, such asto dial the telephone number. Operational data may be retrieved frommemory unit 330 to perform the function. Furthermore, processing unit310 may display the instructional and operational information on display315 for the user's reference and convenience.

Processing unit 310 issues instructional information to RF section 335,to initiate communication, for example, transmit radio signalscomprising voice communication data. RF section 335 comprises a receiverand a transmitter to receive and transmit radio signals. Antenna 340facilitates the transmission and reception of radio signals. Uponreceiving radio signals, RF module 335 may forward and convert thesignals to baseband frequency for processing by processing unit 310. Theprocessed signals would be transformed into audible or readableinformation outputted via speaker 345, for example.

Processing unit 310 is adapted to perform various methods disclosedherein, among other operation. It will be apparent to one skilled in theart that mobile communication device 300 may be readily implementedusing, for example, processing unit 310 or other data or digitalprocessing device, either alone or in combination with external supportlogic. Although the present invention is described in the context ofmobile communication, the present invention may also be used in anywireless communication systems using mobile devices, such as PDAs andlaptop computers equipped with wireless communication capabilities.Moreover, the use of certain terms to describe the present inventionshould not limit the scope of the present invention to certain type ofwireless communication system, such as UMTS. The present invention isalso applicable to other wireless communication systems using differentair interfaces and/or physical layers, for example, TDMA, CDMA, FDMA,WCDMA, and the like.

The preferred embodiments may be implemented as a method, apparatus orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The term “article of manufacture” as used herein refers to codeor logic implemented in hardware logic (e.g., an integrated circuitchip, Field Programmable Gate Array (FPGA), Application SpecificIntegrated Circuit (ASIC), etc.) or a computer readable medium (e.g.,magnetic storage medium (e.g., hard disk drives, floppy disks, tape,etc.), optical storage (CD-ROMs, optical disks, etc.), volatile andnon-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs,SRAMs, firmware, programmable logic, etc.). Code in the computerreadable medium is accessed and executed by a processor.

The code in which preferred embodiments are implemented may further beaccessible through a transmission media or from a file server over anetwork. In such cases, the article of manufacture in which the code isimplemented may comprise a transmission media, such as a networktransmission line, wireless transmission media, signals propagatingthrough space, radio waves, infrared signals, etc. Of course, thoseskilled in the art will recognize that many modifications may be made tothis configuration without departing from the scope of the presentinvention, and that the article of manufacture may comprise anyinformation bearing medium known in the art.

The logic implementation shown in the figures described specificoperations as occurring in a particular order. In alternativeimplementations, certain logic operations may be performed in adifferent order, modified or removed and still implement preferredembodiments of the present invention. Moreover, steps may be added tothe above described logic and still conform to implementations of theinvention.

The foregoing embodiments and advantages are merely exemplary and arenot to be construed as limiting the present invention. The presentteaching can be readily applied to other types of apparatuses andprocesses. The description of the present invention is intended to beillustrative, and not to limit the scope of the claims. Manyalternatives, modifications, and variations will be apparent to thoseskilled in the art.

1-29. (canceled)
 30. A method for establishing a connection between auser equipment (UE) and an associated network, the method comprising:transmitting to the UE a notification indicating either a start of amultimedia broadcast/multicast service (MBMS) broadcast service or anavailability of the MBMS broadcast service, wherein the notificationcomprises an MBMS broadcast identifier which identifies the MBMSbroadcast service and a version of MBMS broadcast service information;receiving a point-to-point radio bearer request message, wherein therequest message comprises a short transmission identifier or anidentifier derived from a temporary mobile group identifier (TMGI) thatidentifies the MBMS broadcast service and further comprises versioninformation associated with the version of the MBMS broadcast serviceinformation; and transmitting to the UE a setup message whichestablishes a point-to-point radio bearer between the UE and thenetwork, wherein the setup message comprises the MBMS broadcastidentifier which is used to identify the radio bearer that carries theMBMS broadcast service.
 31. The method according to claim 30, furthercomprising: receiving a request message identifying the MBMS broadcastservice.
 32. The method according to claim 30, further comprising:establishing or maintaining a signaling connection between the UE andthe network.
 33. The method according to claim 30, further comprising:receiving a setup confirmation message to confirm establishment of theMBMS broadcast service.
 34. The method according to claim 30, whereinthe notification further comprises at least a MODIFIED SERVICESINFORMATION message or an UNMODIFIED SERVICES INFORMATION message. 35.The method according to claim 30, wherein the user equipment (UE) andthe network are configured to operate within a universal mobiletelecommunications system (UMTS).
 36. The method according to claim 31,wherein the request message further comprises a cell update message, aradio resource control (RRC) connection request message or an MBMSmodified service request message.
 37. The method according to claim 30,further comprising: determining the version of the MBMS broadcastservice information using a timing reference associated with the MBMSbroadcast service information.
 38. The method according to claim 37,wherein the timing reference is determined based upon a system framenumber associated with the MBMS broadcast service information.
 39. Themethod according to claim 30, wherein the MBMS broadcast serviceinformation comprises a list of MBMS broadcast service identifiersarranged by appending MBMS broadcast service identifiers received inunmodified services information to MBMS broadcast service identifiersreceived in modified services information.
 40. The method according toclaim 39, wherein the short transmission identifier corresponds to alocation of the MBMS broadcast service identifier within the list ofMBMS broadcast service identifiers.
 41. The method according to claim30, wherein the MBMS broadcast service identifier is related to theTMGI.